Kamu Kurumları Tarafından Hazır Ticari Yazılım Seçiminde Kullanılacak DAR Tabanlı Bir Yöntem

Public institutions generally consider only the features list and the price in tenders while acquiring commercial-of-the-shelf (COTS) software products. Yet non-functional requirements of software often dominate them in terms of cost-benefit analysis and total cost of ownership (TCO). In this paper, we emphasize the non-functional requirements that need to be included in the technical scoring/evaluation in order to select a quality product with low TCO, and how the customer can evaluate those requirements. Existing literature presents the evaluation criteria for non-functional requirements from the developer perspective. The required data for such evaluation is not usually available to the customer. We here define the criteria that the customer can really use for her